Ham Radio 2000 #1

home *** CD-ROM | disk | FTP | other *** search

/ Ham Radio 2000 #1 / Ham Radio 2000.iso / ham2000 / misc / baytrm10 / bayterm.doc < prev next >

Wrap

Text File | 1994-12-23 | 23.5 KB | 515 lines

BayTerm Copyright(c) 1994 Don Lafontaine (VE2UFO) Packet ve2ufo@ve2ike.#mtl.pq.can.noam Internet lafont02@godzilla.cn.ca and Ike Tamigian (VE2IKE) Packet ve2ike@ve2ike.#mtl.pq.can.noam Internet tamigian@godzilla.cn.ca ALL RIGHTS RESERVED. WELCOME TO BayTerm By Raymond Faguy (VE2SJA) Here is an overview of why the BayTerm software was written, and how it works. I got into packet in 1993 with a "Baypack" and "Baycom" software and fell in love with it. In early 1994,thinking I was doing a wonderful thing, I bought a TNC, a PK88 to be exact. Don't get me wrong, this is a very nice machine but I was used to Baycom, and liked the look and feel of it. But then again the TNC does have some nice features. So here I was, moping about the fact that I like my TNC, but I also liked my Baycom. Then, one day, Don says to me "Ok Ray, lets see if I can write something that will cheer you up." You see, Don is a programmer, and never lets anyone forget it. And BayTerm was born. A special thanks to Raymond Faguy (VE2SJA/VE2CIH) and Alfio Ferrara (VE2FAF) for their relentless bug hunting and feature wish lists. Also a special mention to Ike Tamigian (VE2IKE) for jumping aboard and helping out with the coding. Without Ike's help, the KPC3 support would have been a long time down the road. Without their prodding, this program would be a pretty little box on the screen with letters in it. THANKS GUYS! I have one question, does anybody have an MFJ TNC? I'd like to support this one, but I don't know the particulars concerning MFJ's host mode interface. Any help would surely be appreciated. I think that would cover most MAJOR TNC manufacturers. Sorry, the TINY-2 doesn't support host mode. -[ Red in the face dept. ]- Sorry folks, but at this time, there is no way to get to the PK-232/PK-88 maildrop. In a future release, we'll address this problem. For now, you can use a node to loop back to yourself and access your maildrop that way. --------=> License <=-------------------------------------------------------- BayTerm is not a "public domain" program. Copyright (c) 1994 by Don Lafontaine (VE2UFO) and Ike Tamigian (VE2IKE) All rights reserved. BayTerm is shareware. The unregistered version may be freely copied and distributed. The program and/or manual may not be modified in any way and it is not allowed to charge more than the price of a diskette for distribution. You are hereby granted a limited license to use this software for evaluation purposes for a period of 30 days. If you intend to continue using this software after the 30 day evaluation period, you must make a registration payment of $20 in Canadian funds drawn from Canadian banks to: Don Lafontaine -or- Ike Tamigian PO Box 352 Succ. Snowdon Montreal PQ Canada H3X-3T6 --------=> Warranty <=------------------------------------------------------- The authors provide absolutely no warranty, to the extent permitted by applicable law. Except when otherwise stated in writing, the authors and/or other parties provide this program "AS IS" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the program is with you. Should the program prove defective, you assume the cost of all necessary servicing, repair or correction. In no event unless required by applicable law will the authors and/or any other party who may modify and/or redistribute this program be liable to you for damages, including any lost profits, lost monies, or other special, incidental or consequential damages arising out of the use or inability to use (including but not limited to loss of data or data being rendered inaccurate or losses sustained by third parties or a failure of the program to operate with any other programs) this program, even if you have been advised of the possibility of such damages, or for any claim by any other party. --------=> System requirements <=--------------------------------------------- BayTerm will run under MS-DOS 3.x or higher on any IBM PC-compatible computer with at least 370KB of free memory. A harddisk is not required, but is nice to have. On slow systems, e.g. 8088/86 CPU, some functions may not work as expected or may not work at all. BayTerm will automatically detect the type of video adapter in use. MDA, CGA, EGA, VGA and Hercules are supported. No attempt has been made to avoid screen flicker (snow) on CGAs. The TNC must be set to communicate at 9600 baud (TNC to Computer). ABAUD 9600. --------=> REVISION HISTORY <=------------------------------------------------ ß = BETA Version 1.0ß: - First draft, messy code, fast hack. - Added support for the KPC-3 and PK-232(MBX). - Uses TCXL 5.5 for windowing. (This is to change) - Uses a public domain async library (This is to change) Version 1.2ß: - Fixed some windowing bugs. - Added callsign display to the session window. Version 1.3ß: - Fixed more windowing bugs. Version 1.4ß: - Removed KPC support for now. (To be worked on at a later date.) - Upgraded the Window library to TCXL 6.02. - Switched from Microsoft C 8.0c to Borland C++ 3.0 - Finished the window resizing functions - Re-assigned function keys. - Moved the windowing functions from the keyboard loop to the async loop. - Now re-establishes connections on entry to the program. - Fixed most colors for monochrome systems. - Made Exploding windows optional (Faster without it, but it is fancy :) ) - Added dump to file function (ALT-P). - Began writing the .doc file. Version 2.5ß: - Added Multi-session support, virtual windows. - Removed window resizing code. Added full screen monitor window. - Added session activity flags. - Modified dump to file function to allow for different sessions. Version 3.0ß: - Recolored the session flags to be a little more clear. - Fixed screen clearing, on exiting the program. - Added Session Status popup. (ALT-S) Version 3.1ß: - Added session conferencing. (ALT-L) - Re-divided the source code into 3 files. - Added /c command line parameter (E.G.: /cMYCALL) for conferencing. - Fixed a minor bug (Minor??) in the file logging routine. Version 3.2ß: - Code handed off to Ike (VE2IKE) to add the KPC host mode support. - Fixed tiny bug in input routine. - Rewrote both the Connect and File Dump dialog boxes. - Tweaked and tuned the code yet again. --------=> REVISION HISTORY (Cont'd) <=--------------------------------------- Version 4.0ß: - Async library thrown out in favor of Ike's comm code. - Added routine to SERIOS.ASM to allow peeking into the comm buffer. - Ike fixed my blunder in SERIOS.ASM. - Nasty little bug squashed in SERIOS.ASM. - Keyboard idle routine trashed. Rewritten with kbhit() loop. - TNC specific code identified and separated to aid with multi TNC support. - Help screen no longer holds up everything. - Added VIA support for Digipeaters. - Added multiple language support. Version 4.1ß: - KPC3 code re-integrated - Fixed a couple of nasty CR/LF problems with the KPC3 code. Solution: Suppress addition of LF's, and do it ourselves. This is because the KPC3 doesn't add LF's in EVERY packet recv'd! - PK232 and PK88 will now be set to terminal mode on exit. On startup of the program, it will be set to host mode. - Disabled the CTRL-C, CTRL-BREAK and CTRL-ALT-DEL. - Disabled Conference Linking and File Dumping because of fatal bugs. Version 4.11ß: - Fixed faulty current session logic. - Re-enabled Conference Linking and File Dumping. - Fixed a small problem with session data not getting displayed on the current_session. - Fixed small problem in CTRL-C handler. Version 4.2ß: - Added Config file processing for TNC Initialization on entry and exit. BayTerm.INI is used at the start, BayTerm.END at the end. - Disabled Language support for now. - Added /n (Disable TNC Initialization) to the command line. - Fixed problem with Full screen monitor window. - Added ability to link BayTerm conference nodes together. Version 4.3ß: - Fixed problem with Conference Loop detector. - Changed the initialize_tnc function to accept english commands. - Changed colors a little to help with the monochrome monitors. - Added ALT-V. Displays Version information. - Fixed up host mode on entry. It is now forced! - Fixed up terminal mode on exit. Version 4.4ß: - Fixed problem with File Dump, escape works now. - Cursor now goes to a reasonable place on exit. - Tentatively released shareware version (1 user). - Fixed yet ANOTHER problem with the full-screen monitor window. Version 1.0: - Released to the general public as shareware. Version 1.0 pl 1 ß: - Fixed blunder with ALT-F5 and ALT-F1 processing. - Added 'pause' function in send_file(). - Added wildcard processing in File Dump function. - Added path processing, users can execute BayTerm from anywhere. - Added session window scrolling capability. --------=> INSTALLATION <=---------------------------------------------------- Installing BayTerm is easy! Unzip the program into the directory you want BayTerm to reside in. E.G.: cd\ md bayterm cd bayterm pkunzip a:\baytrm10.zip Now what you want to do is run BAYINST from the directory you just created. This will set up the batch file and initialization files needed to run BayTerm. The batch file that is created will be called BT.BAT. You can add this directory to your path so that you can run BayTerm from anywhere. --------=> INTRODUCTION <=---------------------------------------------------- Several local hams (including me) have expressed a wish to have a BAYCOM style terminal program that would work with their full-blown TNC's. This first version is an attempt to fill this need. There are a few command line parameters, here they are: Parameter Example Description ------------------------------------------------------------------------------- /PK88 /pk88 Disable HF support /PK232 /pk232 Enable PK-232 Support. /KPC3 /kpc3 Enable Kantronics KPC3 Support. /50 /50 Use 50 line mode (VGA only). /P<port> /p2 Sets the COM port (DEFAULT: 2) See the section on COM ports. /I<irq> /i3 Sets the COM port IRQ (DEFAULT: 3) See the section on COM ports. /D /d Enable direct screen writes. Not needed with VGA systems. Causes snow on CGA screens. /X /x Enable Exploding Windows All windows will explode onto the screen. Fancy special effect, that all. /A /a Turn alarms off. (ALT-A will turn them back on) /C /cVE2UFO Sets your callsign. Used in conferencing. /S /s25 Session-monitor dividing line. Use this parameter to change the default session and monitor sizes. If you want to be in 50 line mode, you must specify the /50 parameter first. --------=> SPECIFIC REQUIREMENTS FOR TNC'S <=--------------------------------- In order for this program to work properly, certain TNC paramaters have to be set. ** Above all, the TNC must be set to 9600 baud. ABAUD 9600. ** These can be added into the BayTerm.INI file. For AEA type TNC's: 1 - Constamp parameter should be set to OFF (Constamp off) 2 - DCDCONN should be set ON (PK-232). (Dcdconn on) These are optional, but the program was built with these in mind: 4 - Monitor all packets. (Monitor 5 or 6) 5 - Monitor all packets while connected. (Mcon 5 or 6) For Kantronics type TNC's: 1 - Constamp parameter should be set to OFF (Cstamp off) These are optional, but the program was built with these in mind: 4 - Monitor all packets. (Mcom on) 5 - Monitor all packets while connected. (Mcon on) --------=> USING THE PROGRAM <=----------------------------------------------- There are two TNC initialization files you can use to set up your TNC at the start and end of the program. BayTerm.INI is read at the beginning of the program, this file will contain all the commands necessary to set the TNC up for proper operation with BayTerm. Add as many lines as you wish. Comments may be included, and must start with a '#' in column 0. You can also set the TNC parameters on exiting the program, this is done by adding the commands you need to BayTerm.END. This is handy when you use more than one program with your TNC. Now you're ready to run BayTerm, go for it! This is the main terminal screen. Status --> Alt-F1=Help [ ABCDEFGHIJ ] CMD V1200 October 23, 1994 15:21:03 +-[ Input ]-----------------------------------------------------+ | | Input --> | | | | +---------------------------------------------------------------+ +-[ Session 'A' ]-----------------------------------------------+ | | | | | | | | | | Session | | Output --> | | | | | | | | | | | | | | +---------------------------------------------------------------+ +-[ Monitor ]---------------------------------------------------+ | | | | Monitored | | Packets --> | | | | | | +---------------------------------------------------------------+ --------=> ESTABLISHING A CONNECTION <=--------------------------------------- To connect to a station, hit ALT-F3 from an inactive session. You'll see a window asking for a callsign, type the callsign you want, as well as any VIA's you need, and hit enter. The TNC at this point has control over the actual connection. After the connection is established, you'll hear a short beep (If sound is active) and a window will pop up confirming the connection. Check the callsign, it could be someone connecting to you in another session window. The status line will reflect session statuses. White Inactive session. Bright green Active session. Flashing Bright Red New data has arrived (Or new connection). Anything that you type at this point will at first be displayed in the Input area. After you hit enter, it will be copied into the Session area. You can scroll through the active session window by using the UP and DOWN arrow keys. The scroll bar at the right of the session window will reflect your current position in the (virtual) window. After you're done, if you can log off from the system via a menu, do so. In the case of a keyboard to keyboard connection, or a system that has stopped responding to you, hit ALT-F4. This will terminate the session from your end. Keep in mind it is always best, where possible, to terminate a session gracefully. That is, say Bye.. Hitting ALT-F1 at any point will bring up this help window: +-[ Help ]-----------------------------------------------+ | | | F1-F10 Session 1 to 10. | | ALT-F1 This help display. | | ALT-F3 Connect to a station | | ALT-F4 Hard Disconnect | | ALT-F5 Full screen monitor mode. (Toggle) | | ALT-F7 Change packet baud | | ALT-F8 Toggle HF/VHF (PK-232) | | ALT-F10 Exit BayTerm | | ALT-A Toggle Sound | | ALT-C Clear session window | | ALT-P Toggle session filing. | | PG-DN Same as ALT-P | | ALT-S List status of all sessions. | | ALT-K Toggle Command/Converse mode | | ALT-L Link sessions | | ALT-V Display Version | | | | [ Press any key to continue ] | +--------------------------------------------------------+ --------=> SPECIAL KEYS <=---------------------------------------------------- There are a few special keys you can use while in the main terminal screen. Note that the shareware version does not allow you to type in any session other than session 'A'. F1 to F10 This will allow you to switch from one session to another. ALT-F1 This brings up the help screen. (Shown above) ALT-F3 Connect to a station. This brings up a form asking you which station you would like to connect to. +-[ Connect Request ]----------------+ | | | Call: ▓▓▓▓▓▓▓▓▓▓ | | Vias: ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ | | | +------------------------------------+ Simply type in the callsign you want to connect to, including the SSID. E.G.: VE2CIH-1 ALT-F4 Hard disconnect. This is a nasty way of disconnecting from another station, but it's usefull sometimes. ALT-F7 Change packet baud rate. If you are using a TNC with a different baud rate than the default 1200 baud, use this key to get to it. It will cycle between the different speeds. It will be displayed on the status line, at the top of the screen. ALT-F8 If you are using a multi-mode TNC (PK-232), use this key to switch between VHF and HF operation. ALT-F10 Use this key to exit the program. All connections will remain active, so disconnect first if you want them closed. You may also use ALT-X to exit. ALT-A Turns sound on or off. ALT-C Clears the active session window. ALT-P Log session output to a file. This will bring up a form asking you what file you want to log output to. If you want to use the printer, type 'PRN'. +-[ Dump to File ]--+ | | | File: ▓▓▓▓▓▓▓▓▓▓▓▓| +-------------------+ ALT-K Toggles between command and converse mode, as reflected by the status line. If you are not connected to anyone, this will allow you to send UNPROTO packets. --------=> SPECIAL KEYS (Cont'd) <=------------------------------------------- ALT-S This will display all the session statuses. ALT-L This will display all the sessions and allow you to link different sessions together. All packets from a conferencee will be sent to the others automagically. Everything you type on a linked session will include your callsign if you used the /c command line parameter, otherwise NOCALL is displayed. (*DISABLED IN THE SHAREWARE VERSION*) --------=> COM PORTS <=------------------------------------------------------- A few notes about COM port setups. The default BIOS setup for com ports is: PORT IRQ BASE ADDRESS ---------------------------- COM1 4 3f8 COM2 3 2f8 COM3 4 3e8 COM4 3 2e8 As you can see, there would be an interrupt (IRQ) conflict with ports 1 and 3, as well as ports 2 and 4. Normally this is OK, but if you wanted to use these pairs at the same time, it would not work. One reason you would want to use the /I parameter is when you have 3 or more COM ports on your computer. In my setup, I have 3 ports: PORT IRQ BASE ADDRESS ---------------------------- COM1 4 3F8 COM2 3 2F8 COM3 5 3E8 Therefore, because my COM3 port is non-standard, I would use this command line: BayTerm /p3 /i5 This would allow me to use all my ports at once.